Skip to main content link. Accesskey S
  • HCL Logo
  • HCL Connections On-Premise Wiki
  • THIS WIKI IS READ-ONLY.
  • HCL Forums and Blogs
  • Home
  • API Documentation
Search
Community Articles > Deployment Scenarios > IBM Connections V4.5: How to configure Tivoli Access Manager (TAM) V6.1.1.
  • Share Show Menu▼

Recent articles by this author

How to set up embedded Connections Content Manager with Connections 4.5
This procedure describes how to set up Connections Content Manager (CCM) with Connections by using the Embedded installation path.

How to set up Cognos and metrics for Connections 4.5
This document assumes that you do not have Connections 4.5 installed. It describes the procedure to install Cognos and the Cognos fix packs correctly and the Connections installation steps that deal with Cognos integration to get metrics to work against Connections 4.5.

IBM Connections 4.5: How to Deploy a Two Node Cluster of Connections V4.5 on a RedHat (RHEL) Server V6.4 (x86-64bit)
Contents 1. Deployment topology 2. Connections system requirements 3. Middleware installation and configuration 3.1 Install Installation Manager 1.5.3 3.2 Install WAS V8 Deployment Manager (DM) 3.3 Install WAS V8 Applications Server on Node1 and Node2 3.4 Install HTTP Server (IHS) ...

IBM Connections V4.5: How to configure Tivoli Access Manager (TAM) V6.1.1.
Configuring TAM

IBM Connections V4.5: How to configure SPNEGO
Configure IBM® Connections to use SPNEGO for single sign-on (SSO). This configuration permits users to sign in to the Windows desktop and automatically authenticate with Connections.
Community articleIBM Connections V4.5: How to configure Tivoli Access Manager (TAM) V6.1.1.
Added by ~Manny Ekwegenettu | Edited by IBM contributor~Tony Loptumiskiakol on July 31, 2013 | Version 2
  • Actions Show Menu▼
expanded Abstract
collapsed Abstract
Configuring TAM
Tags: TAM 4.5, 4.5_deployment
ShowTable of Contents
HideTable of Contents
  • 1 About this task
  • 2 About the author

About this task


Single sign-on (SSO) enables users to log in to one application of IBM Connections and switch to other applications and resources without having to authenticate again.
There are several different ways to configure SSO. This procedure describes one approach. It uses a WebSphere Application Server LTPA key and WebSEAL Transparent Junctions.

 

About the author
Patrick (Pat) Cadogan has worked for IBM for over a quarter of a century. Pat initially started working at Lotus Development and
focused on the globalization and localization of Lotus products such as Lotus 1-2-3, Freelance, Symphony, Improv and Lotus
Notes/Domino. . IBM acquired Lotus in 1995. In 1998 Pat moved to the IBM Lotus Lab in Massachusetts, US, where he worked on
Lotus Domino for Linux, iSeries and zSeries. After five years in the US Pat returned to the IBM Dublin Lab where he focused on
System Verification Testing (SVT) of various IBM products. Pat has worked on the SVT of IBM Connections V2x, 3x, V4 and now
V4.5. Pat can be reached at pcadogan@ie.ibm.com.

 

  • Actions Show Menu▼


expanded Attachments (1)
collapsed Attachments (1)
Edit the article to add or modify attachments.
File TypeSizeFile NameCreated OnDelete file
application/pdf 98 KB IC45-TAM.pdf 5/30/13, 8:04 PM
expanded Versions (1)
collapsed Versions (1)
Version Comparison     
VersionDateChanged by              Summary of changes
This version (2)Jul 31, 2013, 1:25:38 PM~Tony Loptumiskiakol  IBM contributor
expanded Comments (0)
collapsed Comments (0)
Copy and paste this wiki markup to link to this article from another article in this wiki.
Go ElsewhereStay ConnectedAbout
  • HCL Software
  • HCL Digital Solutions community
  • HCL Software support
  • BlogsDigital Solutions blog
  • Community LinkHCL Software forums and blogs
  • About HCL Software
  • Privacy
  • Accessibility